Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The organizations written policy must include a process for how whitelisted applications are deemed to be allowed.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-213324 | MCAC-PO-000109 | SV-213324r506897_rule | Medium |
| Description |
|---|
| Enabling application whitelisting without adequate design and organization-specific requirements will either result in an implementation which is too relaxed or an implementation which causes denial of service to its user community. Documenting the specific requirements and trust model before configuring and deploying the McAfee Application Control software is mandatory. |
| STIG | Date |
|---|---|
| McAfee Application Control 8.x Security Technical Implementation Guide | 2020-10-02 |
Details
| Check Text ( C-14552r309069_chk ) |
|---|
| Consult with the ISSO/ISSM to review the organizational-specific written policy for the McAfee Application Control software. Verify the written policy includes a process for how applications are vetted and deemed to be allowed. If no written policy exists, this is a finding. If written policy does not include a process for vetting applications before allowing them, this is a finding. |
| Fix Text (F-14550r309070_fix) |
|---|
| Follow the formal change and acceptance process to update the written policy to include a process for how applications are vetted and deemed to be allowed. |